My workaround (iOS-only, where I believe we only see the issue) is to use UIGestureRecognizerRepresentable. It doesn't implement the Gesture protocol, so it can't be used at all of SwiftUI's gesture APIs, only gesture. If you have complex gesture interactions that use highPriorityGesture, simultaneousGesture, etc, it may not be enough. This is a TouchDownGesture (generated by Claude Opus 5) that works for me: https://gist.github.com/juanarzola/c48348bfd34bebdf3369bdf5f652dfaa

This is the workaround that I am currently using, which is just using TipKit's model to drive a popover(). Note that these popovers, in iOS 26, use the iOS 26 LiquidGlass morphing-button popover style. import SwiftUI import TipKit extension View { func popoverTipWorkaround(_ tip: some Tip) -> some View { modifier(PopoverTipWorkaround(tip: tip)) } } private struct PopoverTipWorkaround<T: Tip>: ViewModifier { let tip: T @State private var shouldDisplay = false func body(content: Content) -> some View { content .popover(isPresented: $shouldDisplay) { TipView(tip) .tipViewStyle(NoDismissTipStyle()) .tipBackground(.clear) .presentationCompactAdaptation(.popover) } .task { for await status in tip.statusUpdates { if status == .available { shouldDisplay = true } } } } } private struct NoDismissTipStyle: TipViewStyle { func makeBody(configuration: Configuration) -> some View { VStack(alignment: .leading) { configuration.title configuration.message } .padding() } }

I filed feedback for either this or a similar issue FB15170769 - I reproduced the same Fatal Error but there's no save needed, it happens when a FetchedResultCollection is passed to a SwiftUI List()

@jhokit thank you for this sample project, it was extremely helpful. I worked around SwiftData's Query memory issue using this workaround: https://gist.github.com/juanarzola/dca3c96f1122cb9710e443e40d75b01b The problem is not just when counting, any query will load all the objects. It's a terrible regression, I don't know why it won't get fixed. it's not perfect and just wrote it so it might not have the best naming. Thankfully "willSave" now works so we can write code like this.